Top level for Electronic Flight Folder messages Copyright © 2009-2023 Jeppesen. All rights reserved. Your use of the AOC Bookshelf and all supporting documentation is subject to a separate license agreement between you and Jeppesen, a copy of which is included in the zip file or can be obtained from Jeppesen. The AOC Bookshelf is delivered AS IS without warranty of any kind and is not guaranteed to be free from errors or defects. You rely on the AOC Bookshelf at your own risk. No support for the AOC Bookshelf is implied through its publication. The AOC Bookshelf is intended solely for use as a reference and examples of interfaces to Jeppesen systems. Jeppesen may revise, update or cease publication at any time, without notice. Building to the specifications set forth in the AOC Bookshelf does not mean that your intended integration needs will be met or that an interface will function as documented. We recommend contacting Jeppesen directly to discuss professional services options with respect to production application integration and validation efforts. choice EF003 v5 REQUEST the transformation of the Flight Plan into the ARINC 633-1 Operational Flight Plan, with attachments (optional) EF003 v5 RESPONSE Returns the Flight Plan in the ARINC 633-1, 2 Operational Flight Plan Format, with attachments (optional) EF004 vA Acknowledge receipt of Operational Flight Plan message by the aircraft (via EFB). PUBLISH EF003 v5 REQUEST to transform the provided Flight Plan into the ARINC 633-1 Operational Flight Plan format. REQUEST sequence This is a unique string that is used to correlate messages within a message conversation. choice Choose this group when a formatted (XOP) Flight Plan is available. Flight Plan Id that allows the identification of the associated formatted (XOP) Flight Plan data. EF003 v5 ARINC 633-1 RESPONSE Operational Flight plan and attachments EF004 vA Acknowledge Receipt of Operational Flight Plan message via EFB. PUBLISH sequence Aircraft has received Operational Flight Plan message (EF001)? If so, then "true". If not message was not received, then "false". Not nillable. If a message failed, to be delivered to the aircraft, then the entirety of the message is contained here wrapped in CDATA tags. String to associate to attachment document Example: text weather, NOTAMs, etc. May be a MS Word, .pdf , .jpg (etc) document converted into base64Binary format. This field is nillable. sequence This element contains the complete Flight Plan that must be wrapped in CDATA tags. This element contains Flight Plan Notes associated to the Flight Plan that may be contained in CDATA tags. Flight Release must be rapped in CDATA tags. Documents such as Text Weather, or NOTAMs that are converted into base64 binary format. Operational Flight Plan, based on ARINC 633-1, Section 5.4 format. Wrapped in CDATA tags. Operational Flight Plan, based on ARINC 633-2, Section 5.4 format. Wrapped in CDATA tags. sequence This is a unique string that is used to correlate messages within a message conversation. A633=M633SupplementaryHeader airport name e.g. WASHINGTON DULLES INTL e.g. DepartureAirport, DestinationAlternate, ContingencySavingsAirport A633=M633SupplementaryHeader airport name e.g. WASHINGTON DULLES INTL e.g. DepartureAirport, DestinationAlternate, ContingencySavingsAirport Output of ARINC 633. -1 will always be sent, -2 is optional. This element contains Flight Plan Notes associated to the Flight Plan that may be contained in CDATA tags. Flight Release must be rapped in CDATA tags. Documents such as Text Weather, or NOTAMs that are converted into base64 binary format.